feat(resource-catalog): add ENTITY to ResourceType enum#1704
Closed
msbhavana wants to merge 3 commits into
Closed
Conversation
…d resource support Entity bindings were previously skipped during push because the ResourceType enum lacked an ENTITY member, causing catalog lookups to short-circuit. This meant entity resources could only be created as virtual placeholders. Adding ENTITY to the enum enables proper resource catalog lookups so entities can be created as referenced resources when found in the catalog. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
This PR updates the platform Resource Catalog type model to recognize entity resources and adjusts CLI push tests to reflect the new entity-binding behavior (catalog lookup → referenced resource creation) while preserving skip behavior for truly unsupported virtual kinds.
Changes:
- Added
ENTITY = "entity"toResourceTypein the Resource Catalog models. - Updated the “unsupported virtual kind” test to use
choiceSetinstead ofentity. - Added a new test ensuring an
entitybinding that is found in the catalog results in a referenced resource being created.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| packages/uipath-platform/src/uipath/platform/resource_catalog/resource_catalog.py | Extends ResourceType enum to include ENTITY, enabling catalog lookup for entity bindings. |
| packages/uipath/tests/cli/test_create_resources.py | Updates/expands push behavior tests to validate entity catalog hit → reference creation and keep unsupported-kind skip coverage. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
lucianaparaschivei
approved these changes
Jun 9, 2026
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Contributor
Author
|
Superseded by #1705 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
ENTITY = "entity"to theResourceTypeenum inresource_catalog.pyuipath pushchoiceSetas the unsupported kind example (instead ofentity)test_entity_binding_catalog_hit_creates_referenceto verify entities are properly referencedContext
Entity bindings in
bindings.jsonwere previously skipped during push because theResourceTypeenum had noENTITYmember. This caused_find_in_resource_catalogto short-circuit (returningNone), and sinceentityis also not in thesupported_virtual_kindsset, the binding was silently skipped.With this change, folder-level entities declared in bindings can be properly resolved and linked into Studio Web solutions as referenced resources.
Test plan
uip codedagent pushwith entity binding creates a referenced resource (kind = Entity, type = Native)🤖 Generated with Claude Code